The management interface is not configured with both an ingress and egress ACL.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-17822	NET0992	SV-20209r1_rule		Medium

Description
The OOBM access switch will connect to the management interface of the managed network elements. The management interface can be a true OOBM interface or a standard interface functioning as the management interface. In either case, the management interface of the managed network element will be directly connected to the OOBM network. An OOBM interface does not forward transit traffic; thereby, providing complete separation of production and management traffic. Since all management traffic is immediately forwarded into the management network, it is not exposed to possible tampering. The separation also ensures that congestion or failures in the managed network do not affect the management of the device. If the device does not have an OOBM port, the interface functioning as the management interface must be configured so that management traffic does not leak into the managed network and that production traffic does not leak into the management network

Description

The OOBM access switch will connect to the management interface of the managed network elements. The management interface can be a true OOBM interface or a standard interface functioning as the management interface. In either case, the management interface of the managed network element will be directly connected to the OOBM network. An OOBM interface does not forward transit traffic; thereby, providing complete separation of production and management traffic. Since all management traffic is immediately forwarded into the management network, it is not exposed to possible tampering. The separation also ensures that congestion or failures in the managed network do not affect the management of the device. If the device does not have an OOBM port, the interface functioning as the management interface must be configured so that management traffic does not leak into the managed network and that production traffic does not leak into the management network

STIG	Date
Perimeter Router Security Technical Implementation Guide Juniper	2017-06-29

Details

Check Text ( C-20311r2_chk )
Step 1: Verify that the managed interface has an inbound and outbound filter configured as shown in the following example: interfaces { fe-0/0/2 { description “link to our Management LAN” unit 0 { family inet { filter { input OOBM-ingress-filter; output OOBM-egress-filter; } address 10.1.1.22/24; } } } Step 2: Verify that the ingress filter blocks all transit traffic—that is, any traffic not destined to the router itself. In addition, traffic accessing the managed elements should be originated at the NOC. In the example the management network at the NOC is 10.2.2.0/24. firewall { filter OOBM-ingress-filter { term allow-mgmt { from { source-address { 10.2.2.0/24; } destination-address { 10.1.1.22/32; } } then { accept; } } … … … term default-action { then { syslog; discard; } } } } Step 3: Verify that the egress filter blocks any traffic exiting the management interface that was not originated by the managed elements . Verify that the destination address is the NOC address space. firewall { filter OOBM-egress-filter { term allow-mgmt { from { source-address { 10.1.1.22/32; } destination-address { 10.2.2.0/24; } } then { accept; } } … … … term default-action { then { syslog; discard; } } } }

Check Text ( C-20311r2_chk )

Step 1: Verify that the managed interface has an inbound and outbound filter configured as shown in the following example:

interfaces {
fe-0/0/2 {
description “link to our Management LAN”
unit 0 {
family inet {
filter {
input OOBM-ingress-filter;
output OOBM-egress-filter;
}
address 10.1.1.22/24;
}
}
}

Step 2: Verify that the ingress filter blocks all transit traffic—that is, any traffic not destined to the router itself. In addition, traffic accessing the managed elements should be originated at the NOC. In the example the management network at the NOC is 10.2.2.0/24.

firewall {
filter OOBM-ingress-filter {
term allow-mgmt {
from {
source-address {
10.2.2.0/24;
}
destination-address {
10.1.1.22/32;
}
}
then {
accept;
}
}
…
…
…
term default-action {
then {
syslog;
discard;
}
}
}
}

Step 3: Verify that the egress filter blocks any traffic exiting the management interface that was not originated by the managed elements . Verify that the destination address is the NOC address space.

firewall {
filter OOBM-egress-filter {
term allow-mgmt {
from {
source-address {
10.1.1.22/32;
}
destination-address {
10.2.2.0/24;
}
}
then {
accept;
}
}
…
…
…
term default-action {
then {
syslog;
discard;
}
}
}
}

Fix Text (F-17737r2_fix)
If the management interface is a routed interface, it must be configured with both an ingress and egress ACL. The ingress ACL should block any transit traffic, while the egress ACL should block any traffic that was not originated by the managed network device.